This text is dedicated to the 30th anniversary of QuakeWorld Team Fortress, which the game celebrates on August 24, 2026. From an Australian Apartment to MTFL: The History of QuakeWorld Team Fortress Today, Team Fortress almost automatically means Team Fortress 2 — its colorful characters, Valve videos, hats, and everything else that made the series famous to a mass audience. But eleven years before TF2, and three years before Team Fortress Classic, th ere was a very different Team Fortress. Rough around the edges, incredibly fast, technically simple by today's standards — and unexpectedly deep. It was a modification for the first Quake. That was where Scout, Soldier, Medic, Demoman, Engineer, and Spy first appeared. It was also where players rather quickly realized that a team had to be divided into offense and defense, that defense should be built around a sentry gun, and that sometimes it was easier not to run to the flag at all, but literally fly to it using a concussion grenade or an explosion. Specific tactics emerged for specific maps. A clan culture also grew around all of this surprisingly early — something still far from common for team - based FPS games in the mid - 1990s. There is one feature of QuakeWorld Team Fortress history that makes it especially interesting today. It does not fit neatly into the usual ending: “the game became outdated, and the audience moved on.” In the West, the competitive scene really did graduall y fade away. In Russia, things turned out differently: QWTF kept going, and the Moscow Team Fortress League — MTFL — ran from 1998 to 2009. QWTF Chronicles now calls it the longest - running league in the game's history. But this story did not begin with Quake at all. Before Team Fortress, There Was Fortress In the first half of the 1990s, Robin Walker and John Cook were not professional game designers but Australian programmers who played a lot of games and spent a lot of time tinkering with computers. They had known each other since childhood. Ian Caughley j oined the group through Walker's brother. By today's standards, their gatherings were almost domestic: LAN parties, a dozen or more people, computer towers, heavy CRT monitors — and an ordinary two - bedroom apartment in Melbourne. One of the games that influenced them was an amateur Doom map called Fortress. For its time, it was unusual: two teams, two bases, and the route a player took effectively determined which weapon they received. Even here, players had to decide who would pus h forward and who would stay behind to defend. Much of the ruleset, however, literally depended on the honor system — Doom simply had no way to enforce those rules in code. The amateur Fortress map for Doom It is hard to see anything revolutionary in that today, but in the mid - 1990s the approach was rather strange. A typical multiplayer FPS followed a simple rule: everyone was roughly equal, weapons were placed around the map, and from there the player who mo ved and shot better won. Fortress proposed a different idea: sometimes your role within the team mattered more than your personal score. Walker later explicitly connected the name Team Fortress to this very map. In essence, the future TF developers saw two fundamental elements there at once: a strict division into teams and specialization of players within the same team. One problem remained: instead of having to explain all of this before a match, they wanted to build it directly into the game. The opportunity to do that arrived with the release of Quake. QuakeC: The Reason Team Fortress Could Exist at All Perhaps Quake's greatest gift to modders was not even its fully three - dimensional graphics. id Software allowed game logic to be changed through QuakeC. For Team Fortress, that capability proved crucial. Walker and Cook recalled that they were essentially waiting for the tools to be released. As soon as QuakeC became available, they got to work on TF. The possibilities were on an entirely different level: not merely moving weapons around a map, but definin g a character's speed, health, weapon set, special abilities, and rules for interacting with other players. QuakeC The earliest concept sounded almost mundane: take the familiar Quake weapons and distribute them among different character types. One would be fast but fragile. Another heavy and slow. Several intermediate variants would sit between them. From that seemingly simple idea grew the class system — one of the game's fundamental rules. Today, a class - based shooter surprises no one. In 1996, choosing a class meant making a fairly strict , voluntary sacrifice of versatility. Soldier gets the rocket launcher — but can no longer pick up everything in sight and turn into a regular Quake fighter carrying the entire arsenal. Scout is faster than everyone else, but weaker. Sniper is terrifying a t range, but depends on positioning. Medic has abilities that the other classes simply do not possess. Those limitations, in turn, strengthened teamwork: the capabilities of one class complemented those of another. And the developers did not arrive at a finished formula on day one. In the earliest internal versions of TF, proper team play did not yet exist as a coherent system. Mechanics evolved directly during LAN tests: someone would complain about a particular ele ment, the code would be changed, the server restarted — and a few minutes later they would check whether it felt better. At this stage, Team Fortress looked more like a long - running experiment than a game designed in advance. August 1996: Five Classes and Almost No Advertising Team Fortress became publicly available in August 1996. There is a small historical ambiguity around the exact date. The reconstructed archive of the original files preserves both a release and a Usenet announcement for TeamFortress v1.0 dated August 22, 1996. At the same time, the official Team Fortress Wiki , later recollections by the developers, and the modern QWTF community usually treat August 24 as the birthday. The safest wording, then, is August 22 – 24, while keeping the 24th as the traditional birthday of TF. The first version had only five classes: Scout, Sniper, Soldier, Demoman, and Medic. And there was no grand launch. Cook recalled that the archive, accompanied by a small readme, was simply placed in the modifications directory on ftp.cdrom.com. The mod had been made primarily for their own LAN sessions, so they quickly forgot about publishing it. Then emails from strangers started arriving: when is the next version coming out? After that, the mod began gaining an audience quickly. Team Fortress was not designed as a future hit and was not tailored to a market. The authors first made a game for themselves. Then, suddenly, it turned out that a great many other people wanted it too From there, updates followed one after another. Classes in QWTF As early as August 31, version 1.1 added the Heavy Weapons Guy and an early 2Fort. Pyro appeared in October. Development did not stop after the move to QuakeWorld: Civilian was added in January 1997, while version 2.5 brought Spy and Engineer that summer. By then, the set of archetypes was already surprisingly close to the Team Fortress we recognize today. But the class system alone was not enough: the game needed a map on which those mechanics actually worked. 2Fort: The Map That Was Designed Alongside the Game Itself A modern player recognizes 2Fort almost instantly: two symmetrical bases, an open space between them, battlements, water, interior corridors, and a flag hidden deep inside enemy territory. But that structure did not appear fully formed. The earliest Team Fortress games were played on ordinary Quake deathmatch maps. No flags at all. The special - goal system came later, and the early 2forts was more a map about two opposing fortresses than the CTF layout that would eventually become one of t he defining images of the entire series. The map evolved at the same time as the classes. Sniper appeared — so he needed space for long - range shooting. Defensive classes needed rooms in which their strengths actually made sense. As offense changed, additional routes had to be opened or existing ones reworked. Changing one element forced adjustments to the others. Walker later described this almost literally as co - design: the classes were adjusted to 2Fort, and 2Fort itself was adjusted to the classes. This process can be seen most clearly in 2fort5. The 2Fort map The map's readme , dated November 30, 1997, describes more than a year of testing and redesign. The basement spawn points were moved upstairs: if an attacker managed to kill a defender, they were supposed to get at least a brief window to work with the flag. The corridor n ear the flag was rearranged so the entire defense could not simply be stacked in one place. Spawn rooms were blocked by one - way doors in an attempt to fight respawn camping. Even the amount of health on the map was reduced — in part to make Medic feel more necessary. Arguments about competitive balance were already happening then. Where should the defensive line be? How many seconds of advantage has an attacker earned after a successful kill? Is it too easy to fortify a single room? Can map geometry make one class mand atory and another almost useless? 2Fort became more than just a popular map — it was where the developers effectively worked out many of Team Fortress's core principles. December 1996: Quake Becomes QuakeWorld, TF Becomes QWTF The original Quake had a problem that is easy to underestimate today: the Internet of the mid - 1990s. A modem, high ping, an unstable connection — and controls that did not always do what the player had already told them to do. id Software tried to solve this by creating a separate network branch of Quake called QuakeWorld. According to the Quake release archive , the QuakeWorld server appeared on December 13, 1996, and the QWCL 1.25 client on December 17. Just five days later, on December 22, Team Fortress 2.0 Beta moved to QuakeWorld. This is, in effect, where the history of QuakeWorld Team Fortress — QWTF — begins. For Team Fortress, the transition mattered far more than simply changing clients. Team Fortress depended on the number of people on a server much more heavily than ordinary deathmatch. A duel can be played by two people. TF needs attackers, defenders, and different classes — otherwise the whole structure starts to fall apart. So any imp rovement to Internet play immediately increased the chance of getting a proper match instead of a random shootout. The community grew very quickly. A surviving version of John Cook's official website from late 1996 already contains a list of Team Fortress servers in different countries. TF is described there specifically as a mod that makes players work as a team, while possible objectives include cap turing the flag, defending an area, infiltrating a fortress, and other scenarios. The developers even wrote a separate program that regularly queried Quake servers. According to Walker and Cook's recollections, those numbers were what first made them grasp the true scale of what was happening: Team Fortress was already competing in play er count with Quake's major online modes. That was how a small modification for LAN games gradually acquired an international audience. When Players Started Moving in Ways the Developers Never Intended A large part of QWTF's depth emerged only after release — thanks to the players themselves. The best - known example is the concussion grenade carried by Medic and Scout. The grenade was designed to knock players back. But someone quickly noticed what seems obvious in hindsight: if an explosion throws a person through the air, why not detonate a gr enade next to yourself and use that force as a way to move? The developers did not design the concussion jump as a movement system, but players rapidly turned the mechanic into a fully fledged method of traversal. And, as Cook recalled, techniques like this eventually became one of the central elements of clan play. Rocket jumps, grenade jumps, various forms of acceleration, and later bunnyhopping were mastered in much the same way. At some point, an experienced player stopped seeing a map as merely a collection of rooms and corridors. It was read differently: speed could be preserved here, an explosion could carry you across from there, and this s ection of the defense did not necessarily have to be crossed on foot at all. Arc makes a point of this shift in his history of QWTF : as the competitive scene matured, simple shooting skill mattered less and less , while specialization, movement, routes, and teamwork around the flag mattered more and more. That is the defining character of classic QWTF. The game is extremely fast, but that does not remove its strategic dimension: every mistake is especially costly here. A Scout or Medic can fly through a large part of a base in just a few seconds. One missed shot by a defender — and the flag is already out of the room. But if Soldier, Demoman, and Engineer have taken good positions and play together, that very same narrow passage suddenly turns almost into a wall. This is how the familiar TF division into offense and defense gradually became established. A single match develops in two directions at once. Your offense is trying to dismantle the enemy defense piece by piece, while your own defense is enduring exactly the same pressure on the other side of the map. And the two stories affect each other even t hough the players involved may barely meet. From Pubs to the Competitive Scene Clans were a natural phenomenon in Quake in their own right. But Team Fortress made a clan into something more than simply a group of strong players under the same tag. In TF, gathering several strong shooters was not enough. The team had to agree on who played which class, who held a specific position, which routes the offense would take, and what to do after the flag had been moved. Regular practice sessions appeared, t hen scrims, then official matches. A team became a coordinated system. QWTF Chronicles identifies the match between Clan Erinyes and Wolves Moon, played on 2fort4 on February 15, 1997, as the first known QWTF clan match. Clan Erinyes won. FDT and DragonwarZ appeared, followed by ASTFL, ATFL, IGL:TS, STA, TFCL, and other leagues. Arc calls the period from early 1998 to roughly the middle of 1999 the Golden Era of QWTF — a time when there were especially many strong clans and regular competitions. At the same time, the idea of what constituted strong play was changing too. Early TF still held tightly to its Quake deathmatch heritage. Some leagues counted both captures and frags. On 2fort4, a strong defense could quite realistically force a 0:0 flag score, in which case kills decided the result. But the maps changed, offense became more technical, 2fort5 appeared — and the capture itself became increasingly important. By 1999, some leagues were judging matches entirely by captures, while team tactics were increasingly built around advancing the flag. Step by step, QWTF was breaking away from its deathmatch past. Good shooting alone was no longer enough: a player had to understand what was happening at the level of the entire team. The Team Fortress Paradox: The Authors Left, but the Game Kept Living on Its Own By 1997, Team Fortress had long since stopped being a small hobby project. Walker, Cook, and Caughley founded TeamFortress Software; the company was officially registered in Australia in April of that year. The next step was supposed to be Team Fortress 2. Then the developers met Valve — and the story abruptly changed direction. In March 1998, all three came to Seattle and spent several months working in Valve's office. Walker and Cook later stayed with the company, while Caughley returned to Australia. This branch of the story eventually produced Team Fortress Classic for Half - Li fe. From left to right in the photo: John Cook, Ian Caughley, and Robin Walker — the original Team Fortress development team in 1998. By then, QWTF itself had almost settled into the form in which it is remembered. Version 2.8 was released in May 1998, and 2.9 in the autumn. After the developers left, the community continued developing the game itself. The servers remained. The maps. The clans. Configs. Demos. And, most importantly, players who did not need a new game simply because it was new. There was still more to learn in the old one. This part of the story lasted especially long far beyond Australia and the United States. In Russia. Russian QWTF: The Era of Computer Clubs It is difficult to imagine Russian Quake in the late 1990s without computer clubs. QWTF was no exception. The QWTF.NET archive dates the first Russian Team Fortress tournaments to 1997 and directly connects the spread of the game with computer - club culture. According to recollections from members of the community, it was not limited to Moscow: different cities developed their own teams, their own groups of players, and in some places their own small leagues. A good example is the history of the Moscow clan SD SD clan logo It did not begin as a typical Quake clan at all, but as a Q - Zar team made up of employees of the Moscow company Soyuzdesign. In the autumn of 1997, its members first moved to regular QuakeWorld, then to Team Fortress, and from April 1998 they played active ly in computer clubs. Later, membership was no longer restricted to company employees. Over the clan's entire history, more than sixty people passed through SD. Here, the history of the Moscow community unexpectedly echoed the early development of Team Fortress itself. A few years earlier, Walker, Cook, and their friends had sat together in one apartment in front of CRT monitors. Now almost the same thing was happ ening in Moscow computer clubs: players sat side by side, looked over at neighboring screens, argued about classes and positions, demonstrated new jumps, dissected the match that had just ended — and immediately started the next one. Over time, those groups turned into a full - fledged gaming scene. MTFL: The Moscow Branch of Team Fortress History The history of MTFL — the Moscow Team Fortress League — begins in 1998. The long - time leader of clan SD and coordinator of MTFL — Viktor Yurasov, aka [sd] hunter The Russian history of QWTF developed differently from the Western scene. Following Arc's American chronicle , the Golden Era ends around 1999. After that, the number of players and leagues declines. STA survives until early 2004, Chaos until 2005. The author of the chronicle even calls the match played on January 26, 2005 “the last QWTF game”; symbolically, it b egins on 2fort4 — a reference back to the first known clan match in 1997. But that game was “the last” not for the entire worldwide scene, only for the part of it covered by the American chronicle. In Moscow, people were still playing. QWTF Chronicles now explicitly calls the Moscow Team Fortress League the longest - running QuakeWorld Team Fortress league in the world and dates its original run to 1998 – 2009. It also separately mentions the surviving recordings of MTFL matches — a chance to see that Russ ian style of play not through memories, but in actual demos. By 1998, the creators of Team Fortress were already sitting at Valve and thinking about future versions. Team Fortress Classic was released in 1999. Then other team - based FPS games filled the market, Counter - Strike and Quake III appeared, and new generatio ns of online games followed. And Moscow teams kept launching QuakeWorld Team Fortress anyway. The atmosphere of computer clubs in those years For those players, the game's possibilities had not yet been exhausted. That is why MTFL is not simply another regional league in QWTF history. It illustrates a phenomenon that is rare for online games: a product's commercial era can end while its competitive life continues for many more years, provided the community finds the game system interesting and self - sufficient enough. What Those Players Were Preserving From the outside, QWTF really can look like a very old version of Quake with nine classes somehow bolted onto it. After hundreds of hours of play, familiar maps and mechanics begin to be perceived very differently. A player no longer knows only the rooms and corridors. They know how many seconds it will take before an attacker reaches the flag again. Where Demoman is most likely to place his pipes. Which side Soldier is expecting the next entrance from. When it is be tter to kill Engineer immediately and when it is better to destroy the sentry first. Where an explosion boost turns a long route into a short one. And when Medic should keep pushing through an almost hopeless attack because a flag moved a few meters can so metimes be worth more than one more life saved. That is why two attack attempts that looked identical could accomplish completely different things. The first merely revealed the defensive setup. The second forced Demoman to spend grenades. The third broke the sentry. The fourth dragged the flag into the corridor. The fifth picked it up and threw it a little farther. Only the sixth finally got it outside. In a sequence like that, individual frag statistics could tell you almost nothing about who actually did the decisive work. By the late 1990s, Team Fortress was already demonstrating a principle that would later become fundamental to team - based multiplayer games: the value of an action is not determined by a kill alone. What matters is what it changes for the whole team, and ho w much closer it brings the match objective. A Legacy That Became Bigger Than the Game Itself Today, QWTF is remembered mainly through its more famous successors. Team Fortress Classic received Half - Life and a huge new audience. Team Fortress 2 became one of Valve's most recognizable games, while the nine classes turned into fully realized characters — with voices, personalities, and unmistakable silhouettes. But the core principles of the series had taken shape much earlier. Class asymmetry. Scout — speed. Soldier — versatile combat power. Demoman — area control. Medic, Heavy, Pyro, Spy. Engineer with a sentry. Two bases. An objective that has to be captured. Separate offense and defense. Most importantly, the idea that a fast FPS does not have to make every player the same. On the contrary, a team can consist of people with completely different functions — and the game only becomes deeper because of it. In the summer of 1996, the class - based team shooter as we know it today barely existed as a genre at all. Within a few years, dozens of leagues and hundreds of clans existed around QWTF. Thousands of old matches survive in archives, and enthusiasts still study the maps, players, weapons, and tactical evolution of the game today. MTFL, meanwhile, outlived a significant part of the international infrastructure alongside which it had once emerged. Epilogue: The Match That Never Ended Almost a decade and a half passed after the original era ended in 2009. In 2023, the league returned. Old Russian teams and players appeared on the servers again, and QWTF.NET began publishing results, demos, and videos from new competitions. In October 2023, the first matches of the revived BattleAxe 3v3 League were played; later came new seasons and tournaments The history of QuakeWorld Team Fortress still has no clear ending date. The mod that three Australians made for their own LAN sessions in 1996 outlived Quake as a mass - market online game, the release of Team Fortress Classic, several generations of multiplayer shooters, and the disappearance of almost all the infrastructure wi thin which it had once appeared. And decades later, people still join a server, choose Scout, Medic, Soldier, or Demoman — and run for the same flag again. That is the real significance of QuakeWorld Team Fortress. It is not merely “the ancestor of TF2” and not a museum mod for an old game. Rather, it is one of the early examples of how a successful game system can outlive the technologies and industry trends against which it first appeared. Main Sources Shacknews — Threading the Needle: The Making of Quake Team Fortress. A substantial oral history featuring Robin Walker, John Cook, and Ian Caughley; one of the best sources on the origins of Fortress, QuakeC, the classes, 2Fort, and the developers’ move to Valve. TeamFortress Quake Archive. A reconstruction of the original archives, readmes, and TF release dates from 1996 – 1998. Especially valuable for checking the early versions and the disputed date of v1.0. Quake Official Archive. A reconstruction of QuakeWorld release history, including QWSV on December 13 and QWCL on December 17, 1996. QWTF Chronicles. A vast archive of clan, league, map, and demo history; Arc’s texts on the evolution of QWTF and the international competitive scene are especially useful. It is also the source that calls MTFL the longest - running QWTF league. Original 2fort5 readme. An almost primary - source document on the history of one of TF’s most important maps and the reasons behind its design changes. QWTF.NET. The main useful source for the Russian side of the story: computer clubs, clans, SD, the modern archive, and the revival of the competitive scene. http://dc.qwtf.net — Russian - language Discord community. QWTF is still played here. Acknowledgements Special thanks to David L. Craddock for Threading the Needle: The Making of Quake Team Fortress — an enormous oral history that preserved Robin Walker, John Cook, and Ian Caughley’s recollections of the early years of Team Fortress. Huge t hanks to Arc for QWTF Chronicles and many years of work preserving the history of the QuakeWorld Team Fortress competitive scene — its clans, leagues, maps, matches, and the evolution of the game itself. Thanks to everyone who, over the decades, preserved old versions of Team Fortress, maps, readmes, demos, websites, and archives. Much of QWTF’s early history is accessible today only because of this work. Special thanks to the Russian QWTF community, the players and organizers of MTFL — those who kept this game alive far beyond its original era and continue to play it today. And finally — thanks to everyone who still joins a server thirty years later. Without you, this story truly would have ended many years ago.